Added possibility to have many Sentry instances and different http request mechanism#56
Added possibility to have many Sentry instances and different http request mechanism#56lsuski wants to merge 6 commits intojoshdholtz:masterfrom
Conversation
|
Hi @lsuski - thanks for the contribution. Sorry about not getting back to you sooner. This diff is pretty large. I'd like to merge the features, but I think it's safer (and much easier to review) if we implement the changes in smaller chunks. I have implemented a similar change to yours, to use an executor service already. I'm going to open a GitHub issues to track the individual changes here. |
# Conflicts: # .idea/gradle.xml # build.gradle # sentry-android/build.gradle # sentry-android/sentry-android.iml # sentry-android/src/main/java/com/joshdholtz/sentry/Sentry.java # sentry-app/sentry-app.iml # sentry-app/src/main/java/com/joshdholtz/sentryapp/MainActivity.java
|
I've merged changes from your master branch to my fork. I've changed the way of sending contexts - this functionality is not default now and is available through |
2 participants
I've made some refactorings to achieve my requirements. Firstly I didn't want to use deprecated apache client and I needed some security configuration of http request sending. Secondly I needed to use Sentry in library and to avoid any conflicts I've added possibility to have many Sentry instances. Finally I've made some optimisations, e.g. writing requests as JSON because Java Serialization is very unoptimal on Android, especially that Sentry already used JSON. I've also disabled logging for default - it can be turned on by calling
setDebugLoggingmethod.Review carefully my changes.
Thanks